-
-
Notifications
You must be signed in to change notification settings - Fork 33k
gh-135944: Add a "Runtime Components" Section to the Execution Model Docs #135945
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gh-135944: Add a "Runtime Components" Section to the Execution Model Docs #135945
Conversation
FWIW, I'm going to open a DPO thread about this addition before merging, to make sure there's sufficient visibility. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very much support the idea of clearly explaining this. I hope the comments are not too ignorant to be useful.
@gpshead, I've updated the PR to address your comments at https://discuss.python.org/t/proposal-add-text-to-the-language-reference-about-runtime-components/96922/2, Thanks! |
Thanks @ericsnowcurrently for giving this so much thought. All good by me. Ping me if I ought to signify this myself by resolving each. |
FYI, given the nice break I had from this change, I came back to with fresh eyes and found ways I think it could be more clear. |
@ncoghlan, do you have any thoughts about this new section? FWIW, my intent is to keep the section implementation-agnostic, even if some of the terminology comes from CPython. The described concepts are meant to be conceptual, even if they correspond closely to concrete implementation details. |
I have toyed with the idea of specifying what it means to "call into Python", but that can be addressed separately, if at all. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Couple of minor comments inline, but nothing I'd consider merge blocking.
If you tried to cover all the subtleties, I think you'd end up with something three times as long that was actually worse for the primary topic you're aiming to address (giving folks that aren't already familiar with the way threads and processes work in general the gist of how they work for Python in particular). |
This is really helpful to my understanding, especially of the possible multiplicity (or not) of relationships amongst the separate concepts. It's hard to express this kind of thing accurately and independent of a particular implementation, but I think you have. Thanks for the hard work. |
Thanks @ericsnowcurrently for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14. |
…Model Docs (pythongh-135945) The section provides a brief overview of the Python runtime's execution environment. It is meant to be implementation agnostic, (cherry picked from commit 46a1f0a) Co-authored-by: Eric Snow <[email protected]>
…Model Docs (pythongh-135945) The section provides a brief overview of the Python runtime's execution environment. It is meant to be implementation agnostic, (cherry picked from commit 46a1f0a) Co-authored-by: Eric Snow <[email protected]>
GH-139509 is a backport of this pull request to the 3.14 branch. |
GH-139510 is a backport of this pull request to the 3.13 branch. |
The section provides a brief overview of the Python runtime's execution environment.
This is meant to be implementation agnostic, If that doesn't hold true then we should take a different approach.
📚 Documentation preview 📚: https://cpython-previews--135945.org.readthedocs.build/